Sourced from me.paulschwarz:spring-dotenv's releases.

Release 5.1.0

Install

Recommended: use the BOM to keep versions aligned.

Gradle (BOM + choose one module)

dependencies {
    implementation(platform("me.paulschwarz:spring-dotenv-bom:5.1.0"))
// Choose one:
// developmentOnly("me.paulschwarz:spring-dotenv")
// developmentOnly("me.paulschwarz:springboot3-dotenv")
// developmentOnly("me.paulschwarz:springboot4-dotenv")
developmentOnly("me.paulschwarz:springboot3-dotenv")

}

Maven (BOM + choose one module)

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>me.paulschwarz</groupId>
            <artifactId>spring-dotenv-bom</artifactId>
            <version>5.1.0</version>
            <type>pom</type>
            <scope>import</scope>
        </dependency>
    </dependencies>
</dependencyManagement>

Then add one:

• Spring Framework (no Boot): me.paulschwarz:spring-dotenv
• Spring Boot 3: me.paulschwarz:springboot3-dotenv
• Spring Boot 4: me.paulschwarz:springboot4-dotenv

<dependency>
    <groupId>me.paulschwarz</groupId>
    <artifactId>springboot3-dotenv</artifactId>
    <optional>true</optional>
</dependency>

... (truncated)

Sourced from me.paulschwarz:spring-dotenv's changelog.

[5.1.0] – 2026-01-02

✨ Enhancements

Relaxed binding for springdotenv.* and .env entries is supported only when running under Spring Boot. Plain Spring Framework uses strict key resolution.

Relaxed binding for springdotenv.* configuration

• Full Spring Boot–style relaxed binding is now supported for all springdotenv.* configuration keys.
• Configuration can be supplied interchangeably via:
  • kebab-case (springdotenv.ignore-if-missing)
  • camelCase (springdotenv.ignoreIfMissing)
  • uppercase environment variables (SPRINGDOTENV_IGNORE_IF_MISSING)
• Behavior is delegated to Spring Boot’s Binder, ensuring consistency with native Boot configuration rules.

Relaxed binding for .env file entries

• Keys defined inside .env files now participate in relaxed name resolution when running under Spring Boot.
• This allows seamless access across common naming styles (dots, dashes, underscores) without duplicating entries in .env.
• Behavior aligns with Spring Boot’s native environment-variable resolution semantics.
• In plain Spring Framework applications, .env keys are resolved strictly by exact name.

Deterministic precedence between legacy and renamed keys

• When both legacy and new configuration keys are present:
  • The new canonical key wins.
  • Example:
    springdotenv.exportToSystemProperties overrides the deprecated springdotenv.systemProperties.
• Legacy keys remain supported for compatibility, with clear precedence rules.

---

🧪 Testing

• Added focused smoke tests to validate:
  • Relaxed binding across naming variants
  • Partial configuration scenarios (defaults + overrides)
  • Correct precedence between legacy and canonical keys
• Tests explicitly avoid global system property pollution.

---

🧱 Internal changes

• Introduced a Boot-specific relaxed configuration loader that:
  • Reuses Spring Boot’s binding infrastructure
  • Avoids re-implementing relaxed-binding logic
• Clear separation between:
  • Spring-only behavior (exact keys)
  • Spring Boot behavior (relaxed binding via Binder)

... (truncated)

• dde034e Add back javadoc needed for publishing
• a5d919c Update CHANGELOG for version 5.1.0
• f26b88e Change instruction to use "implementation" for bom and developmentOnly for li...
• 1a93637 #60 Fix regression: Load .env even when exporting to system properties
• ad8cedb #16 Explain relaxed vs strict binding
• 65882d5 #16 Improve relaxed binding implementation
• 35d132d #16 Support relaxed binding
• 2adebf2 disable parallel execution of tests
• b8fd919 encourage the use of "development only" mode
• d730366 fix local publishing version
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)